Chip 1996 November

home *** CD-ROM | disk | FTP | other *** search

/ Chip 1996 November / CHIP Kasım 1996.iso / ms / catapult / catapult.exe / README.TXT < prev next >

Wrap

Text File | 1996-06-24 | 54KB | 1,233 lines

************************************************************************ MICROSOFT« Catapult Server Beta 3 Release Notes ************************************************************************ Thank you for beta testing Microsoft Catapult Server Beta 3. "Catapult" is the code name for this prerelease product. Before installing this product, please review this entire document. It contains important information about installing and using Microsoft Catapult Server Beta 3, and is a supplement to the online documentation that is installed with the product. ************************************************************************ ======================================================================== CONTENTS ======================================================================== * Read This Before You Install * Notes About Server Setup * Notes About the Server * Notes About Client Setup * Notes About Clients * Notes about Logging to an ODBC Database * Acknowledgments ======================================================================== READ THIS BEFORE YOU INSTALL ======================================================================== Before you install Microsoft Catapult Server Beta 3, be sure to use an Internet browser to read the following two chapters from the Microsoft Catapult Server Installation and Administration Guide: * Chapter 2, "Preinstallation Requirements" * Chapter 3, "Installation" The Catapult Server Installation and Administration Guide that contains these two chapters is provided in HTML format and can be viewed with an Internet browser. * If Catapult Server has not yet been installed, you can open the Installation and Administration Guide directly from the Catapult Server compact disc or from a network share. Use an Internet browser to open the file Toc_cat.htm, from the Docs folder on the Microsoft Catapult Server compact disc, or from a shared network directory. For example, if the compact disc is in the computer's D: drive, use your browser to open: File:D:\Docs\Toc_cat.htm Or, if the Catapult Server documentation has been installed on the server WOLFHOUND and made available from a shared network directory called Docs, you could connect your computer to \\Wolfhound\Docs and use an Internet browser to open the file Toc_cat.htm. In this example, if a connection to \\Wolfhound\Docs was set up as the redirected E: drive on your client computer, you could use your browser to open: File:E:\Toc_cat.htm Note: Microsoft Internet Explorer, an Internet browser, is provided with Windows NT Server version 4.0 Beta 2 (which must be installed before you can install Catapult Server). * You also have the option, if Catapult has not yet been installed, of running Setup and installing only the documentation. From the Catapult Server compact disc, run Setup. When the Installation Options dialog box appears, clear all options except the check box for "Catapult HTML Documentation." Once the documentation is installed, you can open it by clicking the Catapult Documentation shortcut in the Catapult Server program group. * If Catapult Server or the Catapult Server documentation has been installed on a remote server, and if your computer has access to that server, you can remotely open the Installation and Administration Guide. ======================================================================== NOTES ABOUT SERVER SETUP ======================================================================== * Prepare the Server for Catapult Server Installation * Be Sure To Disable IP Forwarding * Server Must Have a Pointing Device * Allow Only One IIS Directory * Installing Catapult Server * Add Registry Entry to Support FTP Clients ------------------------------------------------------------------------ Prepare the Server for Catapult Server Installation ------------------------------------------------------------------------ To prepare the server for Catapult Server installation, complete the following tasks in order. 1. Remove any earlier Beta version of Catapult Server. Run the Setup program that was installed with that earlier Beta, and choose the Remove All option. Reboot the server after the beta software is removed. Note: Do not use the Setup program provided on the Catapult Server Beta 3 compact disc to remove an earlier beta version. 2. Upgrade the operating system to Windows NT Server version 4.0 Beta 2. Upgrade from the Windows NT Server version 4.0 Beta 2 compact disc, following the instructions provided with that beta release. Note: With Catapult Server Beta 3, use only the Windows NT Server version 4.0 Beta 2 operating system. Even if one becomes available, do not install a newer version of the operating system. 3. Install Internet Information Server 2.0. For installation instructions, see your documentation for IIS provided with Windows NT Server 4.0 Beta 2. Note: With Catapult Server Beta 3, use only the version of Internet Information Server 2.0 provided with Windows NT Server version 4.0 Beta 2. Even if a one becomes available, do not install a newer version of IIS 2.0. Also, do not use IIS 1.0. 4. Install the operating system service pack. * From the Catapult Server compact disc, open the Beta2sp folder. * Open the folder (Alpha, I386, Mips, or Ppc) appropriate to the server's processor (Alpha AXP, Intel, MIPS, or PowerPC). * Run Update.exe, and follow the on-screen instructions. * After installing the service pack, reboot the server. NOTE: Installation of the service pack is not required for clients. ------------------------------------------------------------------------ Be Sure To Disable IP Forwarding ------------------------------------------------------------------------ If your private network runs TCP/IP, be sure to clear the server's Enable IP Forwarding check box in the Network application. This prevents unauthorized routing from the Internet to your private network (prevents unauthorized IP packets from infiltrating your network). To disable IP forwarding on Windows NT Server 4.0 Beta 2: 1. From the Start menu select Settings, and then click Control Panel. 2. In Control Panel double-click the Network icon. 3. In the Network dialog box click the Protocols tab, select TCP/IP Protocol, and then click Properties. 4. In the Microsoft TCP/IP Properties dialog box, click Routing. 5. Make sure the check box for Enable IP Forwarding is cleared. 6. Click OK, then click OK again. Warning If Windows NT Remote Access Service (RAS) is installed on your gateway after Catapult Server is installed, IP forwarding will be enabled. To ensure a secure network, you should disable IP forwarding after installing the RAS on the server. Other server preparations are described in Chapter 2, "Preinstallation Requirements," of the "Installation and Administration Guide," which can be viewed or printed as described earlier in this release note. ------------------------------------------------------------------------ Server Must Have a Pointing Device ------------------------------------------------------------------------ For this beta release, the Setup program requires that the server have a mouse or other pointing device installed. For information about installing and configuring pointing devices, see your documentation for Windows NT Server Beta 2. ------------------------------------------------------------------------ Allow Only One IIS Directory ------------------------------------------------------------------------ In some rare configurations (especially if the server has been upgraded from previous versions) there may be two separate Internet Information Server directories on the server. Delete the obsolete IIS directory before installing Catapult Server. For example, if an earlier version of IIS was installed in C:\Inetsrv and the current version of IIS is installed in C:\Winnt\System32\Inetsrv, delete the C:\Inetsrv directory. ------------------------------------------------------------------------ Installing Catapult Server ------------------------------------------------------------------------ To install Catapult Server: 1. Log on using a user account that has administrative privileges on the server. 2. From the root directory of the Catapult Server compact disc, run Setup. Or copy the contents of the compact disc to a shared network directory, connect the server to that share, and run Setup. 3. Follow the on-screen instructions. Complete installation instructions are provided in Chapter 3, "Server Installation," of the "Installation and Administration Guide," which can be viewed or printed as described earlier in this release note. ------------------------------------------------------------------------ Add Registry Entry to Support FTP Clients ------------------------------------------------------------------------ Some FTP sites require a user name and password. To support client connections to such sites, after installing Catapult Server add this entry to the server's Registry: HKEY_LOCAL_MACHINE SOFTWARE Microsoft InternetClient Parameters Emailname:REG_SZ:Proxy@ To add this registry entry to the server: 1. On the server, run Run Regedt32.exe and open this key: HKEY_LOCAL_MACHINE SOFTWARE Microsoft 2. Under the Microsoft key add this key: InternetClient 3. Under the InternetClient key add this key: Parameters 4. In the Parameters key add this value: Emailname:REG_SZ:Proxy@ ======================================================================== NOTES ABOUT THE SERVER ======================================================================== * How to Remotely Administer Catapult Server * Setting Client Authentication for the Proxy Service * Grant Access Permissions to IUSR_computername * Use Local Groups with Basic Authentication * The Cache Cannot Be Administered During Service Startup * Cache Allocates Directory Space Equal to the Lowest Allocation * Only HTTP Objects Are Cached * Removing or Adding Cache Directories * Make Sure Cache Directories Are Writeable * Negative Caching * Cache Filtering * Protocols Tested with the RWS Service * Support for Alpha World Clients * Enabling or Disabling Access Control for the RWS Service * For Better Performance, Turn Off IIS Logging * One Default Gateway * Protocol Bindings on Network Adapter Cards Connected to the Internet * SSL Tunneling * Domain Filtering * Server Protection * What to Do if Private Network Performance Slows * The Effect of a Full Disk * Proxy Service Error Messages * SNMP MIB Files * Ping and Tracert * Restart the Service After Establishing a Dial-Up Connection ------------------------------------------------------------------------ How to Remotely Administer Catapult Server ------------------------------------------------------------------------ Using Internet Service Manager, you can connect to another Catapult Server across the network and remotely administer its Proxy and RWS services. You can do this from any server that has the Catapult Server software installed. Or, without installing Catapult Server itself, you can install a few Catapult Server files onto a server or workstation, and then use that server or workstation to remotely administer other Catapult Servers. To configure a server for remote administration without installing Catapult Server: 1. Select a server that already has the Windows NT Server 4.0 or Windows NT Workstation 4.0 operating system installed. 2. If not already installed, install Internet Information Server (IIS) on the server, or Peer Web Services (PWS) on the workstation. 3. On the Catapult Server compact disc, open the folder (Alpha, I386, Mips, or Ppc) appropriate to the computer's processor (Alpha AXP, Intel, MIPS, or PowerPC), and then copy these files to the C:\winnt\system32\inetsrv\admin directory on the server or workstation: Rwscfg.dll Rwsapi.dll W3pcfg.dll W3papi.dll Wspapi.dll Note: The above destination directory is the default location for Windows NT 4.0 installations. If IIS or PWS was not installed into the default location on Windows NT Server 4.0, adjust the destination directory accordingly. 4. From the root directory of the Catapult Server compact disc, copy these files into the same destination directory: w3pcfg.hlp rwscfg.hlp 5. Run Regedt32.exe and edit the computer's registry. Open this key: HKEY_LOCAL_MACHINE SOFTWARE Microsoft INetMgr Parameters AddOnServices And add these two values: Proxy: REG_SZ: w3pcfg.dll Rws: REG_SZ: rwscfg.dll After the computer is set up as described above, you can remotely administer Catapult Server computers by running Internet Service Manager from the Microsoft Internet Server program group. ------------------------------------------------------------------------ Setting Client Authentication for the Proxy Service ------------------------------------------------------------------------ The client authentication method used by the Proxy service is actually set by configuring the WWW service. The selected authentication methods apply to both services. To set or change the client authentication method of the Proxy and WWW services: 1. From Internet Service Manager, open the WWW service properties dialog box and (if not already selected) select the Service tab. 2. Select or clear the options under Password Authentication to specify Anonymous, Basic, and/or Windows NT Challenge/Response authentication. 3. If you enable anonymous logon, make sure a username and password are provided under Anonymous Logon options. Note: The IIS Setup program creates this account during IIS installation and names it IUSR_computername. For example, if the server's name is "DELANEY," The IIS Setup program would create a user account named IUSR_DELANEY. 4. If you enable anonymous logon, also make sure the password in the WWW service properties dialog box is identical to the password entered in User Manager for the IUSR_computername account. Note: The IIS Setup program sets this password during IIS installation. However, if you change the password it must be changed in the WWW service properties dialog box and in User Manager. (You will also want to change it in the FTP and Gopher properties dialog boxes.) For more information about configuring client authentication for the WWW, FTP, and gopher services, see the Installation and Administration Guide for Microsoft Internet Information Server. To view this guide, from the Microsoft Internet Server program group, click Product Documentation. Or, from Internet Service Manager, open the Help menu and click Topics. For information about using User Manager, see your documentation for Windows NT. ------------------------------------------------------------------------ Grant Access Permissions to IUSR_computername ------------------------------------------------------------------------ When Anonymous logon is enabled, the IUSR_computername must be granted access to each Proxy protocol (FTP, gopher, and WWW) in order for any user to receive anonymous access to each protocol. To grant anonymous access to a Proxy protocol (FTP, gopher, or WWW): 1. From the Catapult Server program group, click Internet Service Manager, choose the Proxy service, and click the Permissions tab. 2. Select a protocol from the Permission by Service list, and then click Add. The Add Users and Groups dialog box appears. 3. Select the IUSR_computername account and move it to the Add Names list. For example, if the computer is named ROYCE, add the IUSR_ROYCE account to the Add Names list. Also select all groups and individual users who should be granted access to this protocol, and move them to the Add Names list. 4. Click OK. The Permissions tab returns, and the selected users and groups are displayed in the Right box for the selected protocol. Make sure IUSR_computername is listed. 5. Repeat steps 2-4 for the other protocols. When you finish, from the Permissions tab click Apply, then OK to save the access permissions you have granted. Note: It is also acceptable to add the IUSR_computername account to a group, and then grant permissions for a protocol to that group. ------------------------------------------------------------------------ Use Local Groups with Basic Authentication ------------------------------------------------------------------------ When Basic logon is enabled, do not assign access permissions to individual user accounts. Each user that is to be granted access to a Proxy protocol (FTP, gopher, and WWW) must be a member of a local group on the server. The local group must then be granted access permission for the appropriate protocols. To create and modify groups and user accounts, use User Manager for Domains. For information see your documentation for Windows NT. ------------------------------------------------------------------------ The Cache Cannot Be Administered During Service Startup ------------------------------------------------------------------------ Each time the Proxy service starts the cache performs an integrity check and other tests. The duration of this depends on the size of the cache, the number of objects in the cache, and other variables. In some situations it is possible to start Internet Service Manager, open the Proxy service Properties dialog box, and select the Caching tab before the cache has finished its startup checks. When this occurs an error message will be displayed and you will be unable to administer cache parameters. You can select other Proxy service property tabs (such as Service, Permissions, Logging, and Filters tabs) and administer their parameters. However, to administer the cache parameters you will need to close the Proxy Service Properties dialog box, return to Internet Service Manager, wait until the cache has completed its startup checks, and then reopen the Proxy Service Properties dialog box. ------------------------------------------------------------------------ Cache Allocates Directory Space Equal to the Lowest Allocation ------------------------------------------------------------------------ When administering cache directories, allocate identical amounts of space to each cache directory. For this beta release, the cache allocates disk space on all cache directories using the lowest value set for any of the cache directories. For example, say you use Internet Service Manager to increase to 55MB the amount of space allocated to Dir1. Internet Service Manager shows Dir1 is 55MB, Dir2 is 10MB, Dir3 is 10MB, Dir4 is 10MB, Dir5 is 10MB, with the total cache shown as 95 MB. However, the cache will actually use only 10MB from Dir1. Only 50MB total would be available to the cache. ------------------------------------------------------------------------ Only HTTP Objects Are Cached ------------------------------------------------------------------------ For this beta release FTP and Gopher objects are not cached. Only HTTP objects are cached. ------------------------------------------------------------------------ Removing or Adding Cache Directories ------------------------------------------------------------------------ For this Beta release, removing or adding Proxy service cache directories can, under some conditions, cause the Proxy service to stop. This is an intermittent problem and is dependent on server load. (Note that changing the size of a directory does not cause this condition.) The best solution to this condition is to prevent it, by allocating adequate disk space to the Proxy service cache during Catapult Server installation. For an installed server, any of these three methods can be used to safely add or remove the directories allocated to the cache. * Change the disk allocation by running Setup and assigning additional or fewer drives to the cache. * Use Internet Service Manager to reconfigure the Proxy service cache. Be aware that the Proxy service could stop sometime in the subsequent few hours. If it does, use Internet Service Manager to restart the service. Note: Do not immediately stop and restart the Proxy service after adding or removing directories using Internet Service Manager, If you do, then the new information may not be successfully written to the registry by Internet Service Manager. * Stop the Proxy service, edit registry values to add or remove cache directories, and then restart the Proxy service. The Registry Keys used to define directories are under this path: HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services IasCache Parameters Paths By default, the keys "Path1" through "Path5" are created, each defining "Dir1" through "Dir5." To remove a directory, delete it's key from the registry. To add a directory, create the key and add these two values: CacheLimit:REG_DWORD:<size> CachePath:REGSZ:<path> Where: <size> is the size of the directory, for example 0xa for 10 MB <path> is the fully qualified file name, for example C:\URLCACHE\Newdir If you are adding a directory, you must also manually create the directory on the disk (using a command prompt or Windows NT Explorer). If you remove a directory, you must also manually delete the directory from the disk (using a command prompt or Windows NT Explorer). ------------------------------------------------------------------------ Make Sure Cache Directories Are Writeable ------------------------------------------------------------------------ When adding cache directories, make certain the drive is writeable and the Administrator's group on the server is granted Full Control (read/write permissions) for the directory. Do not assign a cache directory to a read-only drive (such as a compact disc drive). ------------------------------------------------------------------------ Negative Caching ------------------------------------------------------------------------ For this beta release, negative caching is not enabled. Negative caching consists of caching objects that represent HTTP error conditions (not network error conditions) associated with accessing particular URLs. ------------------------------------------------------------------------ Cache Filtering ------------------------------------------------------------------------ For this beta release, the Proxy service must be restarted before changes to the cache filtering configuration take effect. ------------------------------------------------------------------------ Protocols Tested with the RWS Service ------------------------------------------------------------------------ The following protocols have been tested with this beta release of the Catapult Server RWS service. By default, Setup configures the RWS service to enable these protocols, and they appear in the list of services in the Permissions property tab for the RWS Service. * Alpha World * ECHO * Enliven * Finger * FTP * Gaming Zone * HTTP * HTTPS * IRC * NNTP * POP3 * RealAudio * SMTP (client) * Telnet * VDOLive These additional protocols have been tested with this beta release of the Catapult Server RWS service, but are not enabled by default. You can enable them by adding them to the list of services in the Permissions property tab for the RWS Service. * LDAP * MSN (Shuttle Internet client) * SNTP * Time You can add or remove these protocols from the list supported by your server installation. You can also configure and use other protocols that do not appear in this list. The list above is intended only to denote the protocols that were tested prior to this Beta release. For more information about enabling protocols with the RWS service, see Chapter 5, "Server Configuration," in the "Installation and Administration Guide," which can be viewed or printed as described earlier in this release note. ------------------------------------------------------------------------ Support for Alpha World Clients ------------------------------------------------------------------------ For this beta release, if access control for the RWS service is enabled, only users with Administrator privileges on the server can send requests to the Internet using the Alpha World protocol over the RWS service. If access control for the RWS service is disabled, any user can use the Alpha World protocol. For information about configuring access control, see "Enabling or Disabling Access Control for the RWS Service," in this release note. ------------------------------------------------------------------------ Enabling or Disabling Access Control for the RWS Service ------------------------------------------------------------------------ When you enable access control for the RWS service, only those clients that have been assigned permissions for specific protocols (using Internet Service Manager) are able to use the RWS service. When you disable access control, all internal clients are able to use the RWS service. Access control is enabled or disabled using the Catapult Server Setup program. The default is to enable access control. To disable or enable access control for the RWS Service: 1. Start Catapult Server Setup. 2. Complete the Setup dialogs in the normal manner. When the Client Access dialog box appears, under the Remote Windows Sockets Access options set the Disable Access Control option. * To enable access control, clear the Disable Access Control check box. * To disable access control, select the Disable Access Control check box. 3. Click OK in the Client Access dialog box, and then complete Setup in the normal manner. ------------------------------------------------------------------------ For Better Performance, Turn Off IIS Logging ------------------------------------------------------------------------ The information stored in the Microsoft Internet Information Server log is a subset of the information stored in the Catapult Server log. Since the information is duplicated, you can improve performance by turning off IIS logging. To turn off IIS logging, use Internet Service Manager to open the Logging property sheet for the WWW service. Clear the Enable Logging check box. ------------------------------------------------------------------------ One Default Gateway ------------------------------------------------------------------------ A Catapult proxy server computer should have only one IP Default Gateway. The IP address of your default gateway should be configured on your Internet network adaptor card. ------------------------------------------------------------------------ Protocol Bindings on Network Adapter Cards Connected to the Internet ------------------------------------------------------------------------ The server's network adapter cards that are connected to the Internet must be bound only to the TCP/IP protocol. In particular, do not bind IPX/SPX or NetBEUI to the externally connected cards. ------------------------------------------------------------------------ SSL Tunneling ------------------------------------------------------------------------ For this beta release, the Proxy Service does not support SSL. However, the Remote Windows Service does support SSL. To use this through a Web browser, you can install the RWS client software (by running Setup from the Iasclnt share on the server), and then configure your Web browser to not use a proxy server., and install the RWS client. Your client will then be proxied through RWS, and SSL will function. ------------------------------------------------------------------------ Domain Filtering ------------------------------------------------------------------------ For this beta release, domain filtering is not enabled for the RWS Service. However, domain filtering is enabled for the Proxy service. For this beta release, if you implement domain filtering with the Proxy service, it is recommended that you ensure filtering by not allowing users of the RWS service to access HTTP, FTP, and gopher ports. To remove permissions to do this, from Internet Service Manager open the RWS Service, click the Permissions tab, click the Protocols button, and remove HTTP, FTP, and gopher from the listed protocols. ------------------------------------------------------------------------ Server Protection ------------------------------------------------------------------------ For the Proxy service, the option to provide Server Protection is not yet enabled. Server protection returns expired objects from the cache to the client if the requested Internet Server is unavailable. ------------------------------------------------------------------------ What to Do if Private Network Performance Slows ------------------------------------------------------------------------ If performance is slow for RWS client requests to particular servers on the private network, check that the IP addresses of those servers are included in the Local Address Table (LAT). The information in the LAT identifies the range of IP addresses of your private network. If an internal server is not listed in the LAT, RWS clients will remote their connections to it through Catapult Server. To check or correct this condition, run Catapult Server Setup for each Catapult Server in your network, and review the IP address ranges listed in the "Network Configuration" dialog box. Add IP address ranges or individual IP addresses as necessary. Or, you can directly read and edit the Iaslat.txt file, located by default in the C:\ias\clients directory of each Catapult Server. For more information about the LAT, see the "Installation and Administration Guide," which can be viewed or printed as described earlier in this release note. ------------------------------------------------------------------------ The Effect of a Full Disk ------------------------------------------------------------------------ If a hard disk on the server becomes full, the Proxy and RWS services will continue to operate, but logging may be affected for both services, and caching may be affected for the Proxy service. If all disks configured to store the logs are full, no new log entries can be saved. If disk space allocated to the cache is less than the size of an object to be cached, that object will not be cached. Note that running without logging can be considered an non-secure condition. ------------------------------------------------------------------------ Proxy Service Error Messages ------------------------------------------------------------------------ For this Beta release, the Proxy service issues error messages in this form: The Proxy server has encountered an error (xxx) Where xxx is usually a Windows NT error code. For more information about Windows NT error codes, see your documentation for Windows NT. ------------------------------------------------------------------------ SNMP MIB Files ------------------------------------------------------------------------ For this beta release, SNMP MIB files are not provided. ------------------------------------------------------------------------ Ping and Tracert ------------------------------------------------------------------------ The Ping and Tracert utilities will not work with Catapult Server Beta 3. ------------------------------------------------------------------------ Restart the Service After Establishing a Dial-Up Connection ------------------------------------------------------------------------ If the Catapult Server computer uses a dial-up line (for example, to connect to an Internet service provider), the WWW service must be stopped and started again after establishing a connection over the modem. You can stop and restart the WWW service using Internet Service Manager. You can also stop and start the WWW service from the command prompt by issuing these commands: net stop w3svc net start w3svc Stopping and starting the WWW Service also stops and starts the Proxy service. ======================================================================== NOTES ABOUT CLIENT SETUP ======================================================================== * Running the Client Setup Program * Upgrading Beta 2 Proxy Clients to be Beta 3 Proxy Clients * One Directory Created by Client Setup Can Be Deleted * Proxy Configuration on IPX-only Clients * Client Connection to Private ISP After Installing the RWS Client * Configuring RealAudio Clients * Configuring FTP Clients * Upgrading the Operating System on Windows NT Clients ------------------------------------------------------------------------ Running the Client Setup Program ------------------------------------------------------------------------ During Catapult Server Setup, a share named Iasclnt is created on the server. This share contains a client Setup program. The client Setup program: * Configures the client computer to use the RWS service (on the server from which RWS client Setup was run). The client computer is configured (not individual applications). * In addition to configuring the client computer to use the RWS service, if the client's Web browser is Microsoft Internet Explorer or Netscape Navigator for Windows NT or Windows 95, client Setup also attempts to configure the browser to use the Proxy service. If this is not appropriate for that client, you may need to reconfigure the client's Web browser after installing the RWS client software Note: By default, client setup will attempt to configure the Proxy settings of the client's Web browser. However, the parameters and options used by the client Setup program are set during Catapult Server installation. These options include a choice to prevent or allow the client Setup program to configure the client's Web browser. To change the client Setup options, re-run Catapult Server Setup. To configure a client: 1. From the client, connect to the Iasclnt share on the server. 2. From the Iasclnt share, run Setup. If a client's Web browser is not Microsoft Internet Explorer or Netscape Navigator, or if client Setup does not successfully configure a client's Web browser to use the Catapult Server Proxy service, then you must use either use the Internet application in Control Panel or the Web browser's own configuration interface to specify the name of the appropriate Proxy server and the protocol port number (80). For more information about setting up clients, see Chapter 6, "Client Configuration," of the "Installation and Administration Guide," which can be viewed or printed as described earlier in this release note. ------------------------------------------------------------------------ Upgrading Beta 2 Proxy Clients to be Beta 3 Proxy Clients ------------------------------------------------------------------------ Proxy clients of Catapult Server Beta 2 had three DLLs installed: * Wsock32.dll, located in the Iexplore directory (or other Web browser directory). * _wsock32.dll, located in the System directory, and loaded by Wsock32.dll. * Miniprox.dll, located in the System directory, and loaded by _wsock32.dll. When a client computer runs the client Setup program (from the Iasclnt share of a Catapult Server) and installs the Catapult Server Beta 3 client software, the client Setup program removes the Catapult Server Beta 2 client software. If you find that client Setup did not successfully reconfigure your Beta 2 client to use the Catapult Server Beta 3 Proxy service, or if you did not run client Setup and want to manually upgrade a Catapult Server Beta 2 client to connect to a Catapult Server Beta 3 Proxy server, perform these tasks: 1. Search all directories on the client's hard disk for the Wsock32.dll file. Delete all instances of Wsock32.dll EXCEPT those in the System and System 32 directories. (Note that you may need to close your Web browser in order to delete the files.) 2. Remove the _wsock32.dll and Miniprox.dll files from the System directory. 3. Use either the Internet application in Control Panel or the Web browser's own configuration interface to specify the name of the appropriate Proxy server and the protocol port number (80). Note: If you remove the _wsock32.dll and Miniprox.dll files from the System directory but do not remove the Wsock32.dll from the Web browser's directory, the Web browser will not start. To resolve this condition, remove the Wsock32.dll from the Web browser's directory. ------------------------------------------------------------------------ One Directory Created by Client Setup Can Be Deleted ------------------------------------------------------------------------ When an RWS client is configured by running the client Setup program from the Iasclnt Setup program on the server, the client Setup program may leave an empty directory, ~Mssetup.t, on one of the client's drives. This directory is not required and may be deleted. ------------------------------------------------------------------------ Proxy Configuration on IPX-only Clients ------------------------------------------------------------------------ For this beta release, the Web browser of a client running only IPX (not running TCP) will not be able to connect to the Proxy service on Catapult Server if the Proxy server is defined in the browser using a domain or computer name. This can be remedied two different ways: * In the configuration dialog for each client's Web browser, edit the client's Web browser configuration to specify an IP address (not a computer or domain name) for the Proxy. * When installing Catapult Server, in the Catapult Server Setup program's Client Access dialog box, under Proxy Access, enter an IP address instead of a computer or domain name. Then, when a client computer runs client Setup from the server's share, if the client browser is Microsoft Internet Explorer or Netscape Navigator, client Setup attempts to configure that browser to use the IP address of the specified proxy server. Note: When assigning Proxy servers to clients in this manner, balance the load between Proxy servers by appropriately adjusting the number of IPX-only clients assigned to each Proxy server. For more information about using Catapult Server Setup to define client Setup parameters, see Chapter 3, "Server Installation" and Chapter 6, "Client Configuration," in the "Installation and Administration Guide," which can be viewed or printed as described earlier in this release note. ------------------------------------------------------------------------ Client Connection to Private ISP After Installing the RWS Client ------------------------------------------------------------------------ For this beta release, if a client computer installs the RWS client software, it will be unable to use Windows Sockets applications to access any Internet sites through a dial-up connection to a private Internet service provider. (This might occur, for example, if a user has a home computer that is used both to connect to the corporate network and also to a private ISP.) To allow the client computer to use Windows Sockets applications with a private ISP, turn off the RWS client by editing the System.ini file on the client computer. In the Internet Access Server section of System.ini, disable RWS by adding the line "Disable=1" and then reboot the client computer. To turn the RWS client back on (to use the client computer on the corporate network with the RWS service of Catapult Server), remove the "Disable=1" entry from System.ini (or set it to "Disable=0"), and reboot the client computer. The System.ini file can be edited by running Sysedit from a command prompt. For more information about editing the System.ini file and using Sysedit, see the documentation provided with your operating system. ------------------------------------------------------------------------ Configuring RealAudio Clients ------------------------------------------------------------------------ When the ReadAudio player is used with the RWS service, do not configure the RealAudio client to use a Proxy server. When configuring the RealAudio player, in the Proxy tab of the Preferences dialog box, specify no proxy. For more information about configuring RealAudio clients, see Chapter 6, "Client Configuration," in the "Installation and Administration Guide," which can be viewed or printed as described earlier in this release note. ------------------------------------------------------------------------ Configuring FTP Clients ------------------------------------------------------------------------ When connecting from the client to Catapult Server over RWS, some FTP clients must be configured to use "passive transfer" mode. (If an FTP client is not so configured, its connection attempts may fail.) ------------------------------------------------------------------------ Upgrading the Operating System on Windows NT Clients ------------------------------------------------------------------------ If the RWS client software is installed on a client computer that runs the Windows NT operating system, and the operating system is later upgraded, the RWS client software will be disabled. To re-enable the computer as an RWS client, reinstall the RWS client software by running client Setup from the Iasclnt share of a Catapult Server. ======================================================================== NOTES ABOUT CLIENTS ======================================================================== * Do not Install Microsoft Exchange Server on RWS Clients * Logons with 16-bit Client Software * Using the Type Field in FTP URLs * About Gopher Requests ------------------------------------------------------------------------ Do not Install Microsoft Exchange Server on RWS Clients ------------------------------------------------------------------------ For this beta release, do not install Microsoft Exchange Server sofware and RWS client software on the same computer. (However, Exchange client software and RWS client software can be installed on the same computer.) ------------------------------------------------------------------------ Logons with 16-bit Client Software ------------------------------------------------------------------------ A "Domain Credentials" dialog box can appear when attempting a connection using 16-bit client software from computers running the Microsoft Windows 95 and Microsoft Windows for Workgroups operating system. To complete this dialog box and complete the connection request, supply a valid domain name, username and password. ------------------------------------------------------------------------ Using the Type Field in FTP URLs ------------------------------------------------------------------------ For this beta release, do not include the "Type=" field in the URL of an FTP request. ------------------------------------------------------------------------ About Gopher Requests ------------------------------------------------------------------------ For this beta release, when a client sends a gopher request using the Catapult Server Proxy service, the gopher server returns gopher+ tags. ======================================================================== NOTES ABOUT LOGGING TO AN ODBC DATABASE ======================================================================== * Logging to ODBC Databases * Table Fields for Logging * Installing an ODBC Driver and Creating a System DSN * Configuring the Logging Property Sheet ------------------------------------------------------------------------ Logging to ODBC Databases ------------------------------------------------------------------------ When you install Catapult Server, logging to a file is the default logging method. If you prefer to collect logs in a database, you can configure the Proxy and RWS services to do so. You can log to any ODBC-compliant database, such as Microsoft SQL Server version 6.5 or Microsoft Access 7.0. Note: Logging to a database increases the amount of time and resources needed to service Internet requests. Therefore, if your site has heavy traffic, you should consider logging to a file to maximize performance. To log to a database you must: 1. Install the database. 2. Create a table in the database with the necessary fields. 3. Install the ODBC driver for that database (if it wasn't already installed during database installation). 4. Create a System Data Source Name (system DSN) for the database that will receive the logging. 5. Run Internet Service Manager, and configure the Logging property sheet for the service (RWS or Proxy). ------------------------------------------------------------------------ Table Fields for Logging ------------------------------------------------------------------------ In a SQL Server table used for the RWS or Proxy service log, the required fields and their lengths are as follows: "ClientIP" varchar(50) "ClientUserName" varchar(50) "ClientAgent" varchar(100) "ClientAuthenticate" char(5) "logTime" datetime "service" varchar(25) "servername" varchar(50) "referredserver" varchar(100) "DestHost" varchar(255) "DestHostIP" varchar(50) "DestHostPort" int "processingtime" int "bytessent" int "bytesrecvd" int "protocol" varchar(25) "transport" varchar(25) "operation" varchar(255) "uri" varchar(255) "mimetype" varchar(25) "objectsource" varchar(25) "resultcode" int In an Access table used for the RWS or Proxy service log, the required fields and their lengths are as follows: "ClientIP" text(50) "ClientUserName" text(50) "ClientAgent" text(100) "ClientAuthenticate" char(5) "logTime" datetime "service" text(25) "servername" text(50) "referredserver" text(100) "DestHost" text(255) "DestHostIP" text(50) "DestHostPort" Long Integer "processingtime" Long Integer "bytessent" Long Integer "bytesrecvd" Long Integer "protocol" text(25) "transport" text(25) "operation" text(255) "uri" text(255) "mimetype" text(25) "objectsource" text(25) "resultcode" Long Integer ------------------------------------------------------------------------ Installing an ODBC Driver and Creating a System DSN ------------------------------------------------------------------------ Before you can create a System Data Source, an ODBC driver for your database must be installed on the system. The ODBC drivers must be ODBC version 2.5 components. This version of ODBC supports System DSNs (Data Source Names), which allows Windows NT services to use ODBC. ODBC 2.5 is required for using ODBC logging with Microsoft Catapult Server and Microsoft Internet Information Server. You can use the Microsoft Internet Information Server (IIS) Setup program to install the SQL Server ODBC driver. You can also use the Microsoft SQL Server Setup program to install the SQL Server ODBC driver, and Microsoft Access to install the Microsoft Access ODBC driver. Note: To log to an Access database, Catapult Server requires the 32-bit ODBC drivers shipped with Microsoft« Office95 and Microsoft« Access95. The ODBC driver for Microsoft Access 2.0 will not work with Catapult Server. Once ODBC drivers have been installed, you can use them to create system data sources. To create system data sources: 1. From the desktop of the server, click Start, select Settings, and click Control Panel. 2. Double-click the ODBC icon. The ODBC Data Sources dialog box appears. 3. Click the System DSN button. IMPORTANT: Be sure to click the System DSN button. Logging to a database will only work with system DSNs. The System Data Sources dialog box appears. 4. Choose the Add button. The Add Data Source dialog box appears. The installed ODBC drivers are listed. 5. Select an ODBC driver and click OK. A dialog box specific to your driver will appear. 6. Enter the Data Source Name and configure the DSN parameters. The data source name is a logical name used by ODBC to refer to the driver and any other information required to access the data, such as the actual server name or location of the database. Use a unique name for the DSN (do not have a user with the same name). For Microsoft SQL Server, the server name, network address, and network library displayed in this dialog box are specific to your installation. You must enter a server name, but if you do not know what to enter in the network address and network library fields you can accept the defaults. Choose the Option button and specify a database name in the Database Name field. 7. Click OK. The System Data Sources dialog box returns, with the new system data source name added. 8. Click Close. The Data Sources dialog box returns. 9. Click Close. Note: For Microsoft Access, the system DSN is the file name of the database. Microsoft Internet Information Server provides a utility that allows creation of system DSNs on remote servers. This utility can be used to create system DSNs for use with Catapult Server logging. For information, see your documentation for Microsoft Internet Information Server. ------------------------------------------------------------------------ Configuring the Logging Property Sheet ------------------------------------------------------------------------ To configure a service to log to an ODBC database: 1. From Internet Service Manager, double-click the RWS or Proxy service, and then click the Logging tab. 2. Select the Enable Logging check box. 3. Select either Regular Logging (to record only a subset of the available information) or Verbose Logging (to record all available information). 4. Select Log to SQL/ODBC database. 5. In the ODBC Data Source Name (DSN) box, type the exact system DSN that you created for the database that you will be logging to. 6. In the Table field, type the name of the table that you will be logging to. 7. In the User Name and Password fields, type a user name and password that is valid for that database and table. 8. Click Apply, and then click OK. ======================================================================== ACKNOWLEDGMENTS ======================================================================== * This is a Preliminary Document * Copyright Information ------------------------------------------------------------------------ This is a Preliminary Document ------------------------------------------------------------------------ This is a preliminary document and may be changed substantially prior to final commercial release. This document is provided for informational purposes only and Microsoft Corporation makes no warranties, either express or implied, in this document. The entire risk of the use or the results of the use of this document remains with the user. Companies, names, and data used in examples herein are fictitious unless otherwise noted. Microsoft grants the right to copy this document in numbers sufficient for testing and evaluating the accompanying product. ------------------------------------------------------------------------ Copyright Information ------------------------------------------------------------------------ Information in this document is subject to change without notice. Companies, names, and data used in examples herein are fictitious unless otherwise noted. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Microsoft Corporation. Microsoft Corporation may have patents or pending patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. The furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property rights except as expressly provided in any written license agreement from Microsoft Corporation. (c)1996 Microsoft Corporation. All rights reserved. Microsoft, MS, Windows, Windows NT, and other names of Microsoft products referenced herein are trademarks or registered trademarks of Microsoft Corporation. All other product and company names mentioned herein are the trademarks of their respective owners.